home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group96a.txt
/
000158_icon-group-sender _Thu Jul 18 22:31:16 1996.msg
< prev
next >
Wrap
Internet Message Format
|
1996-09-05
|
1KB
Received: by cheltenham.cs.arizona.edu; Fri, 19 Jul 1996 17:02:31 MST
Date: Thu, 18 Jul 96 22:31:16 PDT
From: escargo@skypoint.com
Subject: Icon 9.0/386
To: icon-group@cs.arizona.edu
X-Mailer: Chameleon V0.05, TCP/IP for Windows, NetManage Inc.
Message-Id: <Chameleon.960718223730.escargo@.skypoint.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: icon-group-errors@cs.arizona.edu
Status: O
I am doing some minor development using Icon 9.0 for the 386, using the
Windows memory extender.
I was trying to discover why my include files weren't including and my
link files not linking.
I discovered that there is something about how LPATH and IPATH are treated
that seems to make a difference.
I thought I would be able to do something like this:
set ipath="e:\icon\gprocs e:\icon\procs"
set lpath="e:\icon\gincl e:\icon\incl"
That didn't work. For the include files, I just copied them into the source
directories.
For the links, though, that was more than I wanted to do. I experimented
with different values for ipath. What eventually worked was:
set ipath="..\procs"
As long as the path was relative, it seemed to work, but if it was
e:\icon\procs or \icon\procs it would not.
Did I overlook something in the documentation, or is it not supposed to
work quite this way?
-------------------------------------
Name: David S. Cargo
E-mail: escargo@skypoint.com